OMG IT WORKS ON THE FIRST TRY jeez m8 thats gr8

I feel like that "potential optimization" is quite unnecessary, as, by default MSVC uses SSE2, which will probably dump all the 4 floats into a m128 reg, and divide them. Which wont be much slower than just doing this optimization trick(which we shoudnt, as the compiler will optimize it, especially if we enable fast-math(which will pretty much guarantee us that the compiler will use SSE2 with this trick we've used:

#pragma fast-math push
#pragma fast-math on
// code
#pragma fast-math pop

@Pirulax

tbh I agree, but nobody reads CVector code anyways. Constexpr is needed(at least for the constructor) in CGraphics refactor(somewhere in the end, the sphere thing)

Why is constexpr needed there? The main purpose of constexpr is to compute the result in compile time. That can only happen if the compiler knows about the values used in the method at compile-time, otherwise, it will just inline it at best and won't do any good optimizations.

As stated somewhere, I need this for the CGraphics refactor thingy